Systems and methods for managing controller pilot data link communication (cpdlc) systems

ABSTRACT

Systems and methods for a non-integrated CPDLC solution are provided. In one embodiment, the system includes: a first and second computing system for respectively executing a first and second CPDLC application; a Human Machine Interface coupled to the first and second computing systems, the Human Machine Interface providing access to display screens generated by both the first and second CPDLC applications; and a data authority function that determines a data authority application from the first and second CPDLC applications based on which of the first and second CPDLC applications has a current data authority (CDA) session. The data authority function prevents the first CPDLC application from establishing a concurrent current data authority session when the second CPDLC application is the data authority application. The data authority function prevents the second CPDLC application from establishing a concurrent current data authority session when the first CPDLC application is the data authority application.

BACKGROUND

Two different systems for implementing Controller Pilot Data LinkCommunications (CPDLC) for air traffic control are available forcommercial aircraft today. The first CPDLC system is referred to as theFuture Air Navigation System (FANS), or FANS CPDLC. FANS basedapplications are typically implemented on an aircraft's FlightManagement Computer (FMC), also referred to as the Flight ManagementSystem (FMS), and communicate with air traffic control (ATC) stationsusing text based messages communicated over the Aircraft CommunicationsAddressing and Reporting System (ACARS). The second CPDLC system isimplemented over the Aeronautical Telecommunication Network (ATN) via anaircraft's Communication Management Unit (CMU), also referred to as theCommunication Management Function (CMF). The CPDLC system implementedover the ATN via a CMF is commonly referred to as an ATN CPDLC. Use ofFANS CPDLC versus ATN CPDLC on an aircraft is largely based ongeographical considerations such that an aircraft that travels from aFANS CPDLC region to an ATN CPDLC region would greatly benefit frombeing able to support both CPDLC systems.

There are problems that arise however when fully independent FANS CPDLCand ATN CPDLC systems are available to an aircraft's flight crew. FANSand ATN CPDLC systems share “alerting” approaches when a CPDLC messageis received from a ground controller. In cases where the CMF supports anATN CPDLC application and the FMC independently supports a FANS CPDLCapplication, members of the flight crew may become confused as to whichsystem to access after getting a CPDLC alert. Also, with non-integratedsystems, it is potentially possible to establish two different CPDLCsessions using the different CPDLC systems at the same time anddesignate the two different ATC centers associated with the CPDLCsessions as current data authorities (CDAs). This presents a potentiallydangerous situation. To avoid the dangers posed by having two currentdata authorities, some regulations prohibit having different ATC centerssimultaneously function as current data authorities. Such aconfiguration may further face regulatory certification issues if notresolved and could also create training and flight work-load issues.

For the reasons stated above and for other reasons stated below whichwill become apparent to those skilled in the art upon reading andunderstanding the specification, there is a need in the art for improvedsystems and methods for managing non-integrated CPDLC systems on asingle aircraft.

SUMMARY

The embodiments of the present invention provide methods and systems formanaging non-integrated CPDLC systems on a single aircraft and will beunderstood by reading and studying the following specification.

Systems and methods for a non-integrated CPDLC solution are provided. Inone embodiment, the system includes: a first computing system executinga first CPDLC application; a second computing system executing a secondCPDLC application; at least one Human Machine Interface coupled to thefirst computing system and the second computing system, the HumanMachine Interface providing access to display screens generated by boththe first CPDLC application and the second CPDLC application; and a dataauthority function that determines a data authority application from oneof the first CPDLC application and the second CPDLC application based onwhich of the first CPDLC application and the second CPDLC applicationhas a current data authority session. The data authority functionprevents the first CPDLC application from establishing a concurrentcurrent data authority session when the second CPDLC application is thedata authority application. The data authority function prevents thesecond CPDLC application from establishing a concurrent current dataauthority session when the first CPDLC application is the data authorityapplication.

DRAWINGS

Embodiments of the present invention can be more easily understood andfurther advantages and uses thereof more readily apparent, whenconsidered in view of the description of the preferred embodiments andthe following figures in which:

FIG. 1 is a block diagram of a system for implementing a non-integratedFANS/ATN CPDLC solution of one embodiment of the present invention;

FIG. 2 is a block diagram of a control display unit (CDU) for a humanMachine interface of one embodiment of the present invention;

FIG. 3 a-3 c are block diagrams of displays of notification pages on theCDU of one embodiment of the present invention;

FIG. 4 is a block diagram of a system for implementing anothernon-integrated FANS/ATN CPDLC solution of one embodiment of the presentinvention; and

FIG. 5 is a flow chart illustrating a method of one embodiment of thepresent invention.

In accordance with common practice, the various described features arenot drawn to scale but are drawn to emphasize features relevant to thepresent invention. Reference characters denote like elements throughoutfigures and text.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings that form a part hereof, and in which is shown byway of specific illustrative embodiments in which the invention may bepracticed. These embodiments are described in sufficient detail toenable those skilled in the art to practice the invention, and it is tobe understood that other embodiments may be utilized and that logical,mechanical and electrical changes may be made without departing from thescope of the present invention. The following detailed description is,therefore, not to be taken in a limiting sense.

Embodiments of the present invention address the need for managingnon-integrated CPDLC systems on a single aircraft by providing a systeminterface that allows a user to establish multiple CPDLC sessions.Further, the system allows the user to designate only one of the airtraffic controllers associated with the established CPDLC sessions asthe current data authority and prevents the user from communicating withan air traffic controller that is not the current data authority. Thus,the system allows a user to establish CPDLC sessions with differenttypes of CPDLC systems while preserving safe communications between theuser and air traffic controllers.

FIG. 1 is a block diagram of a system 100 for implementing anon-integrated FANS/ATN CPDLC solution of one embodiment of the presentinvention. System 100 includes a first computing system 110 forexecuting one or more FANS applications 112 including a FANS CPDLCapplication 114, a second computing system 120 for executing one or moreATN applications 122 including an ATN CPDLC application 124, and atleast one Human Machine Interface (HMI) 130 coupled to the firstcomputing system 110 and the second computing system 120. As used inthis specification herein, the terms “non-integrated” or “notintegrated” mean that first computing system 110 implementing FANSapplications 112 and second computing system 120 implementing ATNapplications 122 are separate hardware elements. In someimplementations, where first computing system 110 and second computingsystem 120 are not integrated, both computing systems have access tocommonly used peripheral devices within the aircraft (e.g. audible alarmdevices, human machine interfaces, wireless communication radios) andboth send and receive data over a shared on-board data network.

Human machine interface 130 includes a display device 132 for displayingscreens generated by FANS and ATN CPDLC applications 114 and 124. Also,display device 132 provides a way for a user to interact with humanmachine interface 130. In some embodiments, a user, like a flight crewmember, using display device 132, is able to select forwarded fields ona screen using a cursor controlled interface, such as a multifunctiondisplay. In another embodiment, the user controls the screens on displaydevice 132 using a multipurpose control display unit, such as shown inFIG. 2. FIG. 2 illustrates a control display unit 210 for controllinghuman machine interface 130 that includes a display area 215, aplurality of programmable buttons 220 on either side of the display area215, and a keyboard interface 220. In yet other embodiments, the displaydevice 132 provides aspects of both a multifunction display and amultipurpose control display unit (MCDU) to interface with the user.

In the embodiment of FIG. 1, a user accesses CPDLC screens through humanmachine interface 130, where the human machine interface 130 receivesthe CPDLC screens from FANS applications 112 and ATN applications 122. Aflight crew user, such as an aircraft's pilot, for example, accessessome of the screens to log on to and establish multiple CPDLC sessions.For example, a flight crew user logs on to a screen generated by FANSapplications 112 and establishes a CPDLC session with a FANS enabled airtraffic controller. Soon thereafter and while the CPDLC session with theFANS air traffic controller is established, the flight crew user logs onto a screen generated by ATN applications 122 and establishes a secondCPDLC session with an ATN enabled air traffic controller. Further, auser can access other screens on human machine interface 130, where thescreens are provided by FANS applications 112 and ATN applications 122.

In certain embodiments, human machine interface 130 only allows onecurrent data authority to be established at a time. While a user is ableto establish multiple CPDLC sessions through human machine interface130, the human machine interface 130 only allows the user to designateone of the air traffic controllers associated with a CPDLC session as acurrent data authority. To prevent the user from establishing multipleconcurrent current data authority sessions, human machine interface 130includes a data authority function 134. Data authority function 134keeps track of whether FANS CPDLC applications 114 or ATN CPDLCapplication 124 is in communication with an ATC station designated bythe user as the current data authority. The CPDLC application that is incommunication with the current data authority is referred to herein asthe designated data authority application.

In certain embodiments, data authority function 134 allows a user todesignate which CPDLC session is the data authority application. After auser logs on to multiple CPDLC sessions, human machine interface 130provides an interface through display device 132 requesting that theuser select one of the multiple CPDLC sessions to function as thedesignated data authority application. Upon the selection, dataauthority function 134 notifies the air traffic controller associatedwith the designated data authority application that it is the currentdata authority. For example, when a user establishes CPDLC sessions withboth FANS CPDLC application 114 and ATN CPDLC application 124, humanmachine interface 130 requests that the user designate one of FANS CPDLCapplication 114 and ATN CPDLC application 124 as the data authorityapplication. In another example, where the user designates ATN CPDLCapplication 124 as the data authority application, an air trafficcontroller initiates a CPDLC session through ATN applications 122 andATN applications 122 sends a CDA downlink to the air traffic controllerand ATN applications 122 send a current data authority downlink to theair traffic controller to establish the current data authority session.When the CPDLC session is established between the air traffic controllerand ATN applications 122, data authority function 134 distinguishes theCPDLC session between the air traffic controller and ATN applications122 as the current data authority session.

In an alternative embodiment, when the user establishes multiple CPDLCsessions, data authority function 134 selects one of the establishedCPDLC sessions to function as the data authority application withoutreceiving input from the user. For example, in one implementation, dataauthority function 134 selects the CPDLC application associated with theCPDLC session established first from the ground. For example, if a CPDLCsession is established between an air traffic controller and FANSapplications 112 before a CPDLC session is established between an airtraffic controller and ATN applications 122, data authority function 134designates the CPDLC session between the air traffic controller and FANSapplication 112 as the data authority application. In an alternativeimplementation, the data authority function 134 designates a dataauthority application according to characteristics of the aircraft andthe links available to air traffic controllers. Characteristics includelink quality, equipment quality, user preference, and the like.

When data authority function 134 designates a CPDLC session as a dataauthority application, data authority function 134 prevents thenon-designated CPDLC sessions from establishing a concurrent currentdata authority session with an air traffic controller. For example, incertain embodiments, if data authority function 134 designates FANSCPDLC application 114 as the data authority application, data authorityfunction 134 designates ATN CPDLC application 124 as a stand-by dataauthority application. Because ATN CPDLC application 124 is a stand-bydata authority application, data authority function 134 will prevent theuser, ATN CPDLC application 124, or air traffic controller fromestablishing the air traffic controller as a concurrent current dataauthority. To prevent the establishment of a concurrent current dataauthority session over a stand-by data authority application, dataauthority function 134 limits the availability of screens from thestand-by data authority application, prevents the transmission ofmessages to an air traffic controller, and responds to messages from airtraffic controllers by indicating that the air traffic controller is notthe current data authority.

Data authority function 134 receives screens from the multiple connectedcomputing systems and directs display device 132 to display the screensto the user, where the screens aid the user in communicating with an airtraffic controller designated as the current data authority. When aCPDLC application is the stand-by data authority application, dataauthority function 134 prevents the user from accessing screens from thestand-by data authority application to prevent the user fromcommunicating with the stand-by data authority air traffic controller.When a CPDLC session is established through the stand-by data authorityapplication, data authority function 134 allows the user to view ascreen that indicates that an established CPDLC session is not a CPDLCsession with a current data authority. In some implementations, a dataauthority function 134 allows a user to view screens but prevents theuser from using the screens to send commands through the stand-by dataauthority application.

In certain embodiments, data authority function 134 prevents a stand-bydata authority application from sending messages to an air trafficcontroller. In some implementations, when a CPDLC session isestablished, the air traffic controller assumes that they are thecurrent data authority if the air traffic controller receives messagesfrom a CPDLC application. To prevent the air traffic controllerassociated with a stand-by data authority application from assuming thatthe air traffic controller is the current data authority, data authorityfunction 134 prevents the stand-by data authority application fromcreating messages and transmitting the messages to an air trafficcontroller. At times, however, the stand-by data authority applicationreceives unsolicited messages from an associated air traffic controller.When the stand-by data authority application receives these messagesfrom an air traffic controller, data authority function 134 directs thestand-by data authority application to transmit a message to the airtraffic controller indicating that the air traffic controller is not thecurrent data authority. For example, the stand-by data authorityapplication transmits a “NOT CDA” message to the air traffic controller.Thus, data authority function 134 prevents the stand-by data authorityapplication from establishing a current data authority session with anATC center.

In further embodiments, data authority function 134 designates thestand-by data authority application as the next data authorityapplication. Data authority function 134 changes the next data authorityapplication to the data authority application if the link between thecurrent data authority application and the current data authority endsand there is no next data authority connection with the current dataauthority application, and the stand-by data authority application hasan established CPDLC session. For example, when FANS CPDLC application114 is the current data authority application, data authority function134 designates ATN CPDLC application 124 as the next data authorityapplication when there is no next data authority CPDLC session alreadyestablished through the current data authority application. Thus, whenthe CPDLC session between FANS CPDLC application 114 and the currentdata authority terminates and there are no next data authority CPDLCsessions available through FANS CPDLC application 114, data authorityfunction 134 will set ATN CPDLC application 124 as the data authorityapplication. Further, data authority function 134 designates the airtraffic controller associated with ATN CPDLC application 124 as thecurrent data authority. When data authority function 134 changes astand-by data authority application into a data authority application,data authority function 134 instructs the new data authority applicationto send any current data authority downlink messages to the associatedATC center, which include messages that indicate to the ATC center thatthe ATC center is now the current data authority. Further, dataauthority function 134 allows the new data authority application toreceive and process received uplinks from the newly designated currentdata authority. Also, data authority function 134 allows users to sendmessages to the current data authority through the new data authorityapplication.

FIGS. 3A-3C are examples of display screens on Human Machine Interface130 that indicate to a user whether a CPDLC session through a CPDLCapplication is the data authority application. A user, such as a flightcrew member, can view status screens from the CPDLC applications on thedisplay device 132. Display device 132 receives the screens from therespective CPDLC applications. For example, display device 132 receivesstatus screens of the FANS CPDLC session from FANS CPDLC application 114and status screens of the ATN CPDLC session from ATN CPDLC application124. In certain embodiments, the status screens indicate whether a CPDLCapplication is a data authority application or a stand-by data authorityapplication.

FIG. 3A illustrates (generally at 300 a) a display screen 315 a thatindicates the status of a CPDLC application that is communicating withthe current data authority. In display screen 315 a, a current dataauthority field is shown at 330 a. The current data authority field 330a in display screen 315 a indicates to the flight crew user that theCPDLC application associated with the status screen shown on displayscreen 315 a is the data authority application, and that the dataauthority application communicates with the current data authority EDYY.Further, a next data authority field 340 a instructs the flight crew asto the data authority application that will be established if the CPDLCsession with the current data authority were to end.

Conversely, FIGS. 3B-3C illustrate (generally at 300 b and 300 c)display screens 315 b and 315 c that display the status of a CPDLCapplication that is not communicating with the current data authority.In FIG. 3B, display screen 315 b indicates to a user that the CPDLCapplication associated with the status screen is the stand-by dataauthority application by not displaying a status message of the stand-bydata authority. In display screen 315 b, a current data authority field,shown at 330 b, is blank. The blank current data authority field 330 bindicates to a user that the CPDLC application represented by thedisplay screen is not the data authority application. Further, displayscreen 315 b includes a next data authority field 340 b, which informs auser that a CPDLC session has been established between the stand-by dataauthority application and an air traffic controller. For example, nextdata authority field 340 b informs a user that the associated CPDLCapplication represented by the status screen has established a CPDLCsession with the air traffic control center EDYY and no other NEXT ATCcenter connection has been established with the current dataapplication. Thus, if the link between the data authority applicationand the current data authority application were to end, the air trafficcontroller center EDYY would become the current data authority.

In another embodiment, FIG. 3C illustrates a status screen thatexpressly indicates to a user that the associated CPDLC application isnot communicating with the current data authority and that the CPDLCapplication is the stand-by data authority application. For example,display screen 315 c includes a current data authority field 330 c. Whenthe CPDLC application associated with the screen is the stand-by dataauthority application, current data authority field 330 c expresslyindicates to a user that the associated CPDLC application is notcommunicating with the current data authority by displaying “NOT CDA” toa user. In other implementations, current data authority field 330 cdisplays other messages that explicitly state that the associated CPDLCapplication is the stand-by data authority application. Similar to thescreen shown in FIG. 3B, display screen 315 c includes a next dataauthority field 340 c, which informs a user that a CPDLC session hasbeen established between the stand-by data authority application and anair traffic controller. For example, next data authority field 340 cinforms a user that the associated CPDLC application represented by thestatus screen has established a CPDLC session with the air trafficcontrol center EDYY. Thus, if the link between the data authorityapplication and the current data authority application were to end andthere was not another NDA connection, the air traffic controller centerEDYY would become the current data authority.

FIG. 4 is a block diagram of a system 400 for implementing anon-integrated FANS/ATN CPDLC solution of one embodiment of the presentinvention. System 400 comprises a first computing system 410 forexecuting one or more FANS applications 412 including a FANS CPDLCapplication 414, a second computing system 420 for executing one or moreATN applications 422 including an ATN CPDLC application 424, and atleast one Human Machine Interface (HMI) 430 coupled to the firstcomputing system 410 and the second computing system 420. In one or morealternate embodiments, the FANS functions of the first computing systemmay be implemented by the aircraft's FMC, FMS, CMF, or CMU. Similarly,in at least one embodiment, the ATN functions of the second computingsystem would be implemented by the aircraft's CMF.

Human Machine Interface 430 provides a common display device 432 topresent screens generated by the FANS and ATN CPDLC applications 414 and424 to the aircraft's flight crew. In one embodiment, Human MachineInterface 430 includes a Multifunction Display (MFD) which is a forwardfield graphical display device that graphically displays screens to theflight crew and provides a cursor controlled interface to flight crewusers. In one embodiment, Human Machine Interface 430 comprises aControl Display Unit (CDU) 210 such as described with respect to FIG. 2above.

Unlike the embodiment of FIG. 1, the data authority function (showngenerally at 434-1 and 434-2) does not reside on Human Machine Interface430 but is instead distributed between the first computing system 410and the second computing system 420. Such a configuration would beappropriate where, for example, HMI 430 is a “dumb” display terminallacking processing capabilities (for example, like some MCDU) orotherwise includes only limited processing capabilities. In this case,each of the distributed data authority components 434-1 and 434-2determine whether the respective computing system 410, 420 is the dataauthority application.

Distributed data authority components 434-1 and 434-2 communicate withone another to determine which ATC center is the current data authorityand which CPDLC application is the data authority application. In oneimplementation, the first CPDLC application to establish a session withan ATC center is designated as the data authority application. Further,the data authority component 434-1 or 434-2 associated with the dataauthority application notifies the data authority component 434-1 or434-2 associated with the stand-by data authority application that acurrent data authority session is established. For example, when FANSapplications n establishes a current data authority session, dataauthority component 434-1 communicates with data authority component434-2 on the second computing system 420 to indicate that a current dataauthority session is established. When ATN applications 422 establishesa CPDLC session with an ATC center, data authority component 434-2,having received a notification from data authority component 434-1 thata current data authority session is already established, designates ATNapplications 422 as a stand-by data authority application.

Sometimes, both FANS applications 412 and ATN applications 422 attemptto establish current data authority sessions at the same time. Toprevent the two CPDLC applications from establishing two concurrentcurrent data authority sessions, data authority components 434-1 and434-2 perform logic to assure that only one ATC center is designated asthe current data authority. In one implementation, one CPDLC applicationhas priority over the other CPDLC application. For example, where FANSapplications 412 has priority over ATN applications 422, if FANSapplications 412 and ATN applications 422 concurrently attempt toestablish current data authority sessions, data authority components434-1 and 434-2 communicate with one another and designate the ATCassociated with the FANS application as the current data authority.Further, data authority component 434-2 will prevent ATN applications422 from establishing a current data authority session as describedabove in regards to system 100. In an alternative implementation, wheretwo CPDLC applications attempt to establish concurrent current dataauthority sessions, data authority components 434-1 and 434-2 usefactors such as link characteristics, user preferences, region, andperformance abilities when determining which CPDLC application willestablish the current data authority session.

FIG. 5 is a flow chart illustrating a method for implementing anon-integrated FANS/ATN CPDLC solution of one embodiment of the presentinvention. The method begins at 502 with providing access to displayscreens generated by a first CPDLC application, the first CPDLCapplication executing on a first computing system. The method proceedsat 504 with providing access to display screens generated by a secondCPDLC application, the second CPDLC application executing on a secondcomputing system. For example, in one embodiment, the first CPDLCapplication is a FANS CPDLC application and the second CPDLC applicationis an ATN CPDLC application. A data authority function determines that auser has logged n to both the FANS application and the ATN application.The method proceeds at 506 with determining a data authority applicationfrom one of the first CPDLC application and the second CPDLCapplication, the data authority application being a CPDLC applicationthat establishes a current data authority session with an air trafficcontroller. The data authority function designates one of the CPDLCapplications as a data authority application to limit the system to onlyone current data authority session. When the first CPDLC application isthe data authority application, the method proceeds at 508 withpreventing second CPDLC application from establishing a concurrentcurrent data authority session. When the second CPDLC application is thedata authority application, the method proceeds at 510 with preventingthe first CPDLC application from establishing a concurrent current dataauthority session. The data authority function limits the functionalityof the CPDLC application that is the stand-by data authority applicationto prevent the establishment of more than one concurrent current dataauthority sessions.

Although the embodiments discussed above provide examples utilizing FANSand ATN CPDLC applications running over ACARS and ATN networks,embodiments of the present invention are not limited to just these twoCPDLC and network options. For example, an air traffic control centercan establish CPDLC sessions over an IP network. Further, HMIarbitration between any multiple computing systems used to implementseparate CPDLC solutions can be realized by one of ordinary skill in theart using the teachings provided by this specification.

Several means are available to implement the systems and methods of thecurrent invention as discussed in this specification. These meansinclude, but are not limited to, digital computer systems,microprocessors, general purpose computers, programmable controllers andfield programmable gate arrays (FPGAs) or application-specificintegrated circuits (ASICs). Therefore other embodiments of the presentinvention are program instructions resident on computer readable mediawhich when implemented by such means enable them to implementembodiments of the present invention. Computer readable media includeany form of a physical computer memory storage device. Examples of sucha physical computer memory device include, but is not limited to, punchcards, magnetic disks or tapes, optical data storage system, flash readonly memory (ROM), non-volatile ROM, programmable ROM (PROM),erasable-programmable ROM (E-PROM), random access memory (RAM), or anyother form of permanent, semi-permanent, or temporary memory storagesystem or device. Program instructions include, but are not limited tocomputer-executable instructions executed by computer system processorsand hardware description languages such as Very High Speed IntegratedCircuit (VHSIC) Hardware Description Language (VHDL).

Although specific embodiments have been illustrated and describedherein, it will be appreciated by those of ordinary skill in the artthat any arrangement, which is calculated to achieve the same purpose,may be substituted for the specific embodiment shown. This applicationis intended to cover any adaptations or variations of the presentinvention. Therefore, it is manifestly intended to cover any adaptationsor variations of the present invention. Therefore, it is manifestlyintended that this invention be limited only by the claims and theequivalents thereof.

What is claimed is:
 1. A system for implementing a non-integratedcontroller pilot data link communication (CPDLC) solution, the systemcomprising: a first computing system executing a first CPDLCapplication; a second computing system executing a second CPDLCapplication; at least one Human Machine Interface coupled to the firstcomputing system and the second computing system, the Human MachineInterface providing access to display screens generated by both thefirst CPDLC application and the second CPDLC application; and a dataauthority function that determines a data authority application from oneof the first CPDLC application and the second CPDLC application based onwhich of the first CPDLC application and the second CPDLC applicationhas a current data authority session; wherein the data authorityfunction prevents the first CPDLC application from establishing aconcurrent current data authority session when the second CPDLCapplication is the data authority application; wherein the dataauthority function prevents the second CPDLC application fromestablishing a concurrent current data authority session when the firstCPDLC application is the data authority application.
 2. The system ofclaim 1, wherein the first computing system is executing one or morefuture air navigation system applications including the first CPDLCapplication; and wherein the second computing system is executing one ormore aeronautical telecommunication network applications including thesecond CPDLC application.
 3. The system of claim 1, wherein the dataauthority function is executed within the Human Machine Interface. 4.The system of claim 1, wherein the data authority function is adistributed function having a first component executed by the firstcomputing system and a second component executed by the second computingsystem.
 5. The system of claim 4, wherein the first componentcommunicates with the second component.
 6. The system of claim 1,wherein the data authority function designates the data authorityapplication by receiving a user selection through the Human MachineInterface.
 7. The system of claim 6, wherein the Human Machine Interfaceindicates to a user that the first CPDLC application is not the dataauthority application by displaying a notification page indicating thatan air traffic controller associated with the first CPDLC application isnot the current data authority.
 8. The system of claim 1, wherein thedata authority function prevents the establishment of a concurrentcurrent data authority session by performing at least one of: preventingthe CPDLC application from sending messages to an air trafficcontroller; providing data to the Human Machine Interface to indicate toa user that the CPDLC application is not the current data authorityapplication; and indicating to the air traffic controller associatedwith the CPDLC application that the CPDLC application is not the currentdata authority application.
 9. The system of claim 1, wherein the dataauthority function changes a stand-by data authority application to anext data authority application when the data authority applicationfails to establish a CPDLC session with the next data authority.
 10. Thesystem of claim 1, wherein CPDLC sessions are established through atleast one of: an aircraft communications addressing and reporting system(ACARS) network; an aeronautical telecommunications network; a futureair navigation system network; and an internet protocol (IP) network.11. A method for implementing a non-integrated controller pilot datalink communication (CPDLC) solution, the method comprising: providingaccess to display screens generated by a first CPDLC application, thefirst CPDLC application executing on a first computing system; providingaccess to display screens generated by a second CPDLC application, thesecond CPDLC application executing on a second computing system;determining a data authority application from one of the first CPDLCapplication and the second CPDLC application, the data authorityapplication being a CPDLC application that establishes a current dataauthority session with an air traffic controller; when the first CPDLCapplication is the data authority application, preventing the secondCPDLC application from establishing a concurrent current data authoritysession; and when the second CPDLC application is the data authorityapplication, preventing the first CPDLC application from establishing aconcurrent current data authority session.
 12. The method of claim 11,wherein the first computing system is executing one or more future airnavigation system applications including the first CPDLC application;and wherein the second computing system is executing one or moreaeronautical telecommunication network applications including the secondCPDLC application.
 13. The method of claim 11, wherein determining adata authority application comprises executing a data authority functionthat designates the data authority application from one of the firstCPDLC application and the second CPDLC application.
 14. The method ofclaim 13, wherein the data authority function is a distributed functionhaving a first component executed by the first computing system and asecond component executed by the second computing system.
 15. The methodof claim 11, wherein preventing the establishment of the current dataauthority session comprises: preventing a user from communicating withan air traffic controller through a CPDLC application; providing data toa Human Machine Interface to display to a user that the CPDLCapplication is not the data authority application; and indicating to anair traffic controller associated with the CPDLC application that theair traffic controller is not the current data authority.
 16. The methodof claim 15, wherein the Human Machine Interface indicates to a userthat the air traffic controller is not the current data authority bydisplaying on a notification page an indication that the air trafficcontroller is not the current data authority.
 17. The method of claim11, further comprising: determining that a CPDLC session between thedata authority application and the current data authority ended and isnot a next data authority session established through the data authorityapplication; designating a stand-by data authority application as thenew data authority application, the stand-by data authority applicationbeing a CPDLC application in communication with an air trafficcontroller.
 18. A computer readable data storage device having computerexecutable code for a data authority function that controls thefunctionality of a first controller pilot data link communication(CPDLC) application and a second CPDLC application, the methodcomprising: providing access to display screens generated by a firstCPDLC session through a first CPDLC application, the first CPDLCapplication executing on a first computing system; providing access todisplay screens generated by a second CPDLC session through a secondCPDLC application, the second CPDLC application executing on a secondcomputing system; determining a data authority application from one ofthe first CPDLC application and the second CPDLC application, the dataauthority application being a CPDLC application that communicates with aCurrent Data Authority (CDA); when the first CPDLC application is thedata authority application, preventing the second CPDLC application fromestablishing a concurrent current data authority session; and when thesecond CPDLC application is the data authority application, preventingthe first CPDLC application from establishing a concurrent current dataauthority session.
 19. The computer readable data storage device ofclaim 18, wherein determining the data authority application comprisesexecuting a data authority function that designates the data authorityapplication from one of the first CPDLC application and the second CPDLCapplication.
 20. The computer readable data storage device of claim 19,wherein the data authority function is a distributed function having afirst component executed by the first computing system and a secondcomponent executed by the second computing system.